home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d8
/
qmqmpc34.arc
/
PCBUD202.DOC
< prev
next >
Wrap
Text File
|
1990-09-20
|
12KB
|
318 lines
---------
PCBUD.COM
---------
- VERSION 2 -
PCBoard Upload - Download
This program is an adaptation of David Terry's Program of
February 26, 1985 (found on many BBS's as QMPCBSCR.ARC). The
motivation to make the changes was prompted by a change in PCBoard
software from v12 to v14. The changing of the 1k-Xmodem protocall
name from "Y" to "O" made QSCRIPT2 obsolete. So, this fill-in program
came to exist.
Version 2.0 was written to run under Qmodem v4.0. If you
don't have Qmodem v4.0 yet, get it and register it! Scripts run
noticeably faster on my XT under Qmodem 4.0 than they did under 3.1.
This program is public domain. Feel free to copy it,
distribute it, whatever. David Terry deserves much of the credit for
placing SCRIPT.PAS in the public domain. All I did was modify the
source code slightly to suit my desires.
This program is guaranteed to do absolutely nothing. Use it
at your own risk. I have tested it and find it to be a useful tool
FOR ME. I will not be responsible for any losses you may suffer from
the use of this tool.
Chuck Seyboldt
02-01-1989
WHAT IT DOES: ------------------------------------------------------
PCBUD is a program which writes QMODEM SCRIPT segments. These
segments will perform automatic file uploading and downloading to any
BBS running PCBoard v12 or PCBoard v14 software. The SCRIPT has been
tested for downloading from PCBoard v10 and seems to work....but no
promises!
WHAT YOU MUST DO: --------------------------------------------------
^^^^
Run PCBUD.COM from the directory where your QMODEM will look
for scripts. PCBUD puts it's script segments into the directory that
you are logged onto when you call PCBUD. *** IMPORTANT ***
It is allowable to place PCBUD into another directory that is in your
PATH, but you MUST call PCBUD while you are logged onto your QMODEM
script directory.
You will be prompted for a BBS identifier. This is optional.
I use this feature so as to be able to create unique script segments
for the boards I frequent. You will know if you need this feature.
You will be prompted for the name of your u/l-d/l directory.
This is the directory that Qmodem downloads to and uploads from. The
program only supports one directory for both functions.
When you are presented with the selection menu, you have six
choices:
A for an ASCII message upload (message deleted after
upload to avoid repetition and ease housekeeping)
N for an ASCII message upload (message retained in
case you plan to use it again)
(PLEASE: read the section below before attempting ASCII u/l's)
U for upload a file
D for download a file
L for writing a segment that logs off PCBoard
(this also quits PCBUD)
Q for leaving PCBUD
(or a CR alone to quit)
I believe the prompts in PCBUD are clear enough that you
will navigate without trouble.
DEFAULTS are set up as follows:
--------
u/l and d/l directory = \QM\DL \ You get these if you
u/l and d/l protocall = Z > don't enter anything
script segment name = UD.SEG / to the contrary.
An empty CR will terminate the event or the program at other times.
You will have to gain access to a Pascal compiler if you want to
change defaults. Or, you could employ a keyfake program (such as
keyfake or stackey) to pass your defaults to PCBUD.
SCRIPT FEATURES
------ --------
The QMODEM Script code that PCBUD generates contains a fair
amount of error-trapping. For example, if it doesn't see "Command"
when it wants to, it sends a "^M" then waits 5 seconds....then sends
another "^M", and continues until it sees "Command". If the carrier is
lost during the script execution, that error is trapped as well. The
script will terminate.
The QMODEM Script code that PCBUD generates will make sure
that your requested Uploads exist on your disk. If you asked to
upload a file that isn't in your u/l-d/l directory, the script goes to
the next event.
The QMODEM Script code that PCBUD generates is not heavily
commented. It is pretty simple to follow though.
*****************
!***** NO NO'S *****! <***** NO NO'S *****> !***** NO NO'S *****!
*****************
DO NOT use a " in upload descriptions. This will write
Qmodem Script that won't work.
DO NOT use a " as a character in a filename. DOS won't
allow it and the generated script won't work.
DO NOT attempt a one character BBS identifier or a BBS
identifier with an illegal filename character.
*******************************************************************
HOW TO INTERFACE THE SCRIPT SEGMENTS WITH YOUR QMODEM SESSIONS
There are many ways to do this. One of them is to call a
short script while online. The name of that short script might be
XFER.
XFER -------------------
DOS "cd \qm\scr" ; Your script dir
DOS "pcbud"
SCRIPT UD.SEG ; Runs the script segment
; (that PCBUD wrote)
DOS "DEL \qm\scr\UD.USD" ; Rename for further use
DOS "REN \qm\scr\UD.SEG UD.USD" ; "just in case!"
For those of you who want a script generator for logging on
to a BBS, I suggest you copy the following .LOG file as a script. It
will faithfully log you onto a PCBoard v12 or v14 everytime. The
only assumption it makes is that you have your password in the dialing
directory.
Then, you may chain to a previously prepared UD.SEG from
within the PCB14.LOG auto log-in script as follows:
PCB14.LOG --------------
TURNOFF CAPTURE
TIMEOUT 60 ABORT ; Logon TIMEOUT
WHEN "=no change?" "^~^M"
WAITFOR "nter)=no? "
SEND "y q ns^MChuck Seyboldt^M$PASSWORD^M" ; Put in YOUR name
TIMEOUT 60 ABORT
WHEN "inue? " "^M"
WHEN "=yes? " "n^M"
WHEN " (NS)?" "n^M"
WHEN "More? " "n^M"
WAITFOR "mmand? "
WHEN
NOTE << CONNECTED TO $BOARD >>
; Qscript handler begins here...
; ┌─────────────────────────── Change <--to your Qmodem
; │ ^^^^^^ Script directory
; -------
EXIST \qm\scr\UD.SEG UDSCRIPT ; Test for u/l segment
GOTO S_END ; Exit if segment not found
UDSCRIPT:
NOTE
NOTE The file UD.SEG has been detected
NOTE PCBoard u/l & d/l handler now executing...
NOTE
SCRIPT UD.SEG ; Call u/l script segment
PAUSE 2000
GETSCR
DOS "DEL \qm\scr\UD.USD"
DOS "REN \qm\scr\UD.SEG UD.USD"
; --------
; ^-------------------- Change these too!!!!!
PUTSCR
S_END:
RETURN
ABORT:
SEND "^M^~^~^X^~^~^M^~^~G^M"
HANGUP
---------------------------------------------------------------------
I offer a significant CAUTION if you follow the Chained
script route.
IF you integrate this way, BE SURE to include a TIMEOUT for
*EVERY* WAITFOR. I found out the hard way. Bizzare results are in
store if you fail to include the correct TIMEOUTS. It is important
to have these TIMEOUTS even before the "Qscript handler" begining.
Don't be alarmed. If your script is identical to the above
code then all should run just fine.
****** ASCII STUFF ******************************************************
First the cautions: the ASCII u/l feature is a little tricky.
| If you use a FAKEY or STACKEY command in your Qmodem/Zmodem batch |
| files to avoid striking a key after a manual Zmodem transfer then the |
| ASCII u/l feature MUST be run before any Zmodem use. Otherwise, the |
| stacked keystroke(s) will be sent as the first line(s) of your ASCII |
| message. This makes the message to ALL (and could be embarrassing). |
Since Qmodem 4.0 returns to terminal after a Zmodem transfer,
you are not likely to run into the above problem while using PCBUD 2.
To successfully send a message with the script you must
adhere to a strict layout of your ASCII message. A sample message
follows:
Joe Gezhundheit
Sample ASCII Message
n
Hi Joe,
This is a sample of correctly formatted ASCII text that can be
automatically uploaded with a Qmodem script. After the script sends
an "E" to cause PCBoard to look for a text entry, the script waits for
the To (Enter)=`ALL'? prompt. Then it sends this message, first the
receivers name, then the subject, then r for receiver only (or n for
no message security), then the body of the message. It is important
that there are no empty lines in the message or PCBoard will think the
message is over before it really is. But if you've done ASCII u/l
before you know about this. Really quite easy to make a message with
the correct structure. I hope you get as much use out of this program
as I'm getting. And.... please make suggestions or requests to your
heart's content. This tool should be convenient to use.
.
Thanks for your time. I sure do appreciate it!
.
Sat 12-31-1988 17:59:14 Chuck·S
---------------------------------------------------------------------
Files included in this package:
PCBUD200 PAS \ Source code for PCBUD u/l-d/l generator
PCBUD200 COM > Compiled (with TURBO PASCAL v3.0)
PCBUD DOC / This document
-----------------------------------------------------------------------
--------- REVISION HISTORY --------------------------------------------
1-11-89 First public u/l as PCBUD10.ARC
1-12-89 Corrected ASCII u/l sequence. WAITFOR ", (SC)? " was
WAITFOR "(S), (SC)? ". This failed on PCBoard v14.
Corrected to allow upper case command input.
Renamed to PCBUD101.ARC (limited distribution).
1-22-89 Eliminated PCBUDM.* (monochrome version)
and the original script generator (SCRIPT.ARC).
Renamed to PCBUD102.ARC
2-05-89 Revised to run under Qmodem v4.0
Added "delete" and "no-delete" ASCII options.
Added a check to insure u/l descriptions are under
45 characters in length.
Revised TIMEOUTS after uploads. Cosmetic.
Added error trap for host upload disk full.
Added "IF $OFFLINE ..." error trapping.
Added Xmodem CRC protocall (don't ask).
Added Ymodem-G protocall.
Renamed to PCBUD200.ARC
4-11-89 Moved PAUSE to occur before UPLOAD or DOWNLOAD
command to avoid problems with Zmodem.
7-4-89 Changed code to eliminate need for pressing CR
after choosing command option.
Added PACESPEED to ASCII uploads to keep host from
barfing from too rapid a transfer.
Better color handling. Now resets the colors to
where they were rather than imposing white on black
after PCBUD error messages or log-off screen.
Nicer logoff handling. Aborted logoffs don't reset
your screen colors.
Renamed to PCBUD202.ZIP